Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start noting what's up and what goals have been met #799

Merged
merged 5 commits into from
Feb 25, 2023
Merged

Conversation

rocky
Copy link
Member

@rocky rocky commented Feb 24, 2023

I should have started this earlier and we should have started a longer discussion of this.

But hey this is a start. I want to have something in place for the 6.0.0 release.

Your comments and ideas are welcome.

I seem to recall something around \! that involved precedence that was deferred that might go on the list.

Copy link
Contributor

@mmatera mmatera left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. What we could do later would be to create discussions for each of the topics in "FUTURE.rst", and then link them in the file.

Regarding the issue of pattern matching, @rljackobson talked about certain possibilities here:Mathics3/mathics-omnibus#14

If he is up for it, I guess it could be possible to start by trying to decouple a little bit more the pattern matching code from the rest of the mathics-core, and then see if it is possible to replace some part with the existing python libraries without breaking the tests in the CI.

@rocky
Copy link
Member Author

rocky commented Feb 24, 2023

LGTM. What we could do later would be to create discussions for each of the topics in "FUTURE.rst", and then link them in the file.

Good idea - I'll start doing that and adjust this to point to that.

@rocky
Copy link
Member Author

rocky commented Feb 24, 2023

@mmatera Ok - I have made basically the most minimum stab at this. Feel free to add add or start discussions. just commit on top of this with the links. Sometime before release, I merge whatever has been accumulated. I mostly wanted to give people a heads up and get something start here, on this aspect I should have been documenting better.

Mention in PAST that we have been moving towards more modern Python practices
@rocky rocky merged commit d799526 into master Feb 25, 2023
@rocky rocky deleted the update-FUTURE branch February 25, 2023 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants